Previous Next Tracker index See it online !

(324/330) 1775 - XML javacc parser prints out lots of crap to stdout

Try editing an XML file and forget the closing tag of one of your elements,
and parse. You get this in the standard output.
the error is also properly handled and displayed in errorlist.
It comes from javacc-generated code.

8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: xml.parser.javacc.ParseException: Encountered " The Loader creates a new context, and sets itself as a context" at line 66, column 5.
8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: Was expecting:
8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: <TAG_START> ...
8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0:
8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: at xml.parser.javacc.XmlParser.generateParseException(XmlParser.java:677)
8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: at xml.parser.javacc.XmlParser.jj_consume_token(XmlParser.java:557)
8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: at xml.parser.javacc.XmlParser.Tag(XmlParser.java:280)
8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: at xml.SideKickTagHighlight.getMatch(SideKickTagHighlight.java:95)
8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: at org.gjt.sp.jedit.textarea.TextArea.updateStructureHighlight(TextArea.java:5666)
8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: at org.gjt.sp.jedit.textarea.TextArea.access$900(TextArea.java:75)
8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: at org.gjt.sp.jedit.textarea.TextArea$4.actionPerformed(TextArea.java:6698)
8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: at javax.swing.Timer.fireActionPerformed(Timer.java:312)
8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: at javax.swing.Timer$DoPostEvent.run(Timer.java:244)
8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:251)
8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: at java.awt.EventQueue.dispatchEventImpl(EventQueue.java:733)

Submitted	ezust - 2014-02-06 05:12:22.709000	Assigned	kerik-sf
Priority	5	Labels
Status	pending	Group
Resolution	fixed

Comments

2014-02-06 16:37:25.247000 ezust	- Description has changed: Diff: ~~~~ --- old +++ new @@ -1,4 +1,7 @@ -It comes from javacc-generated code, but does it really have to be printed to stdout, or can we properly catch the exception? +Try editing an XML file and forget the closing tag of one of your elements, +and parse. You get this in the standard output. +the error is also properly handled and displayed in errorlist. +It comes from javacc-generated code. 8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: xml.parser.javacc.ParseException: Encountered " The Loader creates a new context, and sets itself as a context" at line 66, column 5. 8:11:29 PM [AWT-EventQueue-0] [error] AWT-EventQueue-0: Was expecting: ~~~~ - Group: -->
2014-03-06 07:41:53.139000 kerik-sf	This is caused by a stray pe.printStackTrace() in xml/parser/javacc/XmlParser.jj I'll fix it and regenerate the javacc parser.
2014-03-06 07:42:16.840000 kerik-sf	- assigned_to: Eric Le Lay
2014-03-06 21:08:18.654000 kerik-sf	- status: open --> pending-fixed
2014-03-06 21:08:19.071000 kerik-sf	fixed in [r23429]
2014-03-10 23:19:13.575000 ezust	nice that the stack traces are gone, but the error message which correctly shows up in the ErrorList is still unnecessarily printed to Stdout.